Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/next-env.d.ts`:
- Line 3: Remove the manual import line import "./.next/types/routes.d.ts"; from
the auto-generated next-env.d.ts file (do not edit next-env.d.ts directly), and
instead add the generated types path (for example ".next/types/**/*.ts" or
include ".next/types" in typeRoots) to your tsconfig.json "include" or
"typeRoots" so the routes types are picked up without modifying next-env.d.ts.

In `@apps/web/public/locales/de/translation.json`:
- Line 34: The German locale file contains English placeholder strings for
several keys (e.g., "k1f07c90") which causes mixed-language UI; for each
referenced key ("k1f07c90" and additionally the keys at lines noted: those
corresponding to positions 95, 210, 226, 244, 281, 309, 354, 366) either provide
proper German translations for the values or remove the keys so the app falls
back to English intentionally; update the translation values in
apps/web/public/locales/de/translation.json ensuring each key's value is valid
German text (or delete the key entries) and keep the key names unchanged.

In `@apps/web/public/locales/es/translation.json`:
- Line 34: The Spanish locale contains English placeholder strings (e.g., key
"k1f07c90") that will show mixed-language UI; update each listed key ("k1f07c90"
plus the other affected keys referenced in the comment) by replacing the English
value with the correct Spanish translation, or remove the keys if you intend to
rely on English fallback; ensure you only commit fully translated values for
keys like k1f07c90 so Spanish users receive a consistent localization.

In `@apps/web/public/locales/fr/translation.json`:
- Line 34: Several keys in the French locale (e.g., "k1f07c90" and the other
listed keys for the new template-cut strings) are still English; update each
key's value to a proper French translation or remove the key if you intend to
rely on English fallback, ensuring no English placeholders remain in apps/web
public locales/fr/translation.json; locate the keys (like "k1f07c90" and the
other eight keys mentioned) and either replace the English text with French
translations or delete the entries, then run the i18n validation/test to confirm
no missing translations.

In `@apps/web/public/locales/id/translation.json`:
- Line 34: The Indonesian locale file contains English placeholder values (e.g.,
key "k1f07c90") that must be replaced with proper Indonesian translations or
removed; update apps/web/public/locales/id/translation.json by translating the
listed keys (k1f07c90 and the other keys at the mentioned positions) into
Indonesian (or delete the keys if you intend to rely on English fallback), then
run the i18n validator/linter to ensure no English strings remain in the id
locale and commit the cleaned translations.

In `@apps/web/public/locales/it/translation.json`:
- Line 34: Replace the English values with proper Italian translations for the
listed keys in apps/web/public/locales/it/translation.json: set k1f07c90 ->
"Impossibile generare la bozza del modello", k371fd2a0 -> "Generazione bozza del
modello in corso...", k6c4c8ae0 -> "Importa prima le risorse visive", k713d4cc5
-> "Bozza del modello generata", k79cf0712 -> "Risorse audio", k88fdb5ec ->
"Modelli con un clic...", k96ebf9b -> "Vai a Media", kaab263db -> "Sostituire la
timeline corrente?", kafb2473b -> "Risorse visive"; update the JSON values for
these keys accordingly and ensure punctuation and capitalization match existing
translation style.

In `@apps/web/public/locales/ja/translation.json`:
- Line 34: Several keys in the Japanese locale contain English placeholders
(e.g., "k1f07c90") and should not be checked in as English; locate the keys
including "k1f07c90" and the other new template-related keys added in this
change and either replace their English string values with proper Japanese
translations or remove the keys if you intend to rely on English fallback, then
run the i18n extraction/validation step to ensure there are no missing
translations.

In `@apps/web/public/locales/ko/translation.json`:
- Line 34: The Korean locale contains English placeholder strings (e.g., the key
"k1f07c90" with value "Failed to generate template draft"); replace these
English values with proper Korean translations for each affected key (or remove
the keys if you intend to rely on English fallback), making sure to update the
values in the ko translation JSON and keep the keys intact (or consistently
omitted) for the other reported entries as well so the Korean locale contains no
English UI text.

In `@apps/web/public/locales/pt/translation.json`:
- Line 34: The Portuguese locale contains English placeholder strings (e.g., key
"k1f07c90" with value "Failed to generate template draft" and eight other
template-cut keys added to the pt translation file) which must be translated or
removed; update each offending key in the Portuguese translation JSON to a
proper Portuguese string (or delete the key if you intend to rely on English
fallback), ensuring the values for "k1f07c90" and the other newly added template
keys are replaced with correct Portuguese translations and that the JSON remains
valid.

In `@apps/web/public/locales/ru/translation.json`:
- Line 34: The listed translation entries in
apps/web/public/locales/ru/translation.json (keys k1f07c90, k371fd2a0,
k6c4c8ae0, k713d4cc5, k79cf0712, k88fdb5ec, k96ebf9b, kaab263db, kafb2473b)
still contain English strings; replace each English value with the appropriate
Russian translation (use the Italian locale entries as a reference for meaning
and tone), ensuring proper grammar and context for UI template-generation
messages and keeping JSON string formatting intact.

In `@apps/web/public/locales/vi/translation.json`:
- Line 34: Several i18n entries in the Vietnamese translations are still in
English; update the JSON values for the keys "k1f07c90", "k94", "k207", "k223",
"k241", "k277", "k305", "k350", and "k362" (use the exact keys shown in the
diff/file) to proper Vietnamese strings, ensuring you replace the English
phrases with accurate Vietnamese translations, preserve the existing JSON key
names and punctuation, and validate the file remains valid UTF-8 JSON after
edits (no trailing commas or broken quotes).

In `@apps/web/src/lib/commands/timeline/template/generate-template-cut.ts`:
- Around line 12-16: In execute(), savedState currently holds a direct reference
from EditorCore.getInstance().timeline.getTracks(), which allows later mutations
to leak into undo; replace that assignment so savedState =
structuredClone(editor.timeline.getTracks()) to capture an immutable deep copy
(keep rest of logic, e.g., editor.timeline.updateTracks(this.tracks) unchanged)
and ensure the savedState type supports the clone so undo() restores the exact
snapshot.

In `@apps/web/src/stores/keybindings-store.ts`:
- Around line 15-16: The code unsafely casts getDefaultShortcuts() to
KeybindingConfig allowing actions that require args (e.g.,
generate-template-cut) to be assigned to shortcuts; update the initialization of
defaultKeybindings so you first filter the result of getDefaultShortcuts() to
only include keybindable actions (i.e., actions that do not require runtime
args) before casting/assigning. Implement or use a predicate like
isKeybindable(action) and apply it when building the mapping returned from
getDefaultShortcuts(), referencing defaultKeybindings, getDefaultShortcuts,
KeybindingConfig, ShortcutKey and any action identifiers (e.g.,
generate-template-cut) so only valid actions become keyboard shortcuts. Ensure
the filtered object matches KeybindingConfig shape before assignment.

In `@docs/plans/2026-03-17-one-click-video.md`:
- Line 13: Change the task headings that use `###` directly after the H1 to one
level lower (`##`) to satisfy markdown-lint MD001; specifically update the
heading "Task 1: 建立一键成片生成器的测试骨架" and the other task headings that currently
start with `###` (the subsequent task headings referenced in the review) to use
`##` so there is no H1→H3 jump, keeping the rest of heading hierarchy intact.

---

Nitpick comments:
In `@apps/web/src/lib/auto-edit/generate-template-cut.ts`:
- Around line 167-168: The current audio element duration fallback in the
audioAssets.map callback uses template.imageDuration (see AudioElement
construction and the duration constant), which is semantically wrong for audio;
update the template shape to include a dedicated defaultAudioDuration (or at
least use a longer numeric fallback like DEFAULT_AUDIO_DURATION) and change the
fallback expression from template.imageDuration to template.defaultAudioDuration
(or the new constant) so audio files without metadata receive an appropriate
audio-specific duration.